Description

Nuking config rules fails if there is no remediation config. Add step to check existence of remediation configs before nuking.

# Found AWS Resources
┌─────────────────────────────────────────────────────────────────────────────────┐
| Resource Type    | Region         | Identifier                        | Nukable |
| ------------------------------------------------------------------------------- |
| config-rules     | ap-southeast-2 | encrypted-volumes                 | -       |
└─────────────────────────────────────────────────────────────────────────────────┘

 WARNING  THE NEXT STEPS ARE DESTRUCTIVE AND COMPLETELY IRREVERSIBLE, PROCEED WITH CAUTION!!!

Are you sure you want to nuke all listed resources? Enter 'nuke' to confirm (or exit with ^C) : nuke
  ERROR   Failed to delete remediation configuration w/ err NoSuchRemediationConfigurationException: No RemediationConfiguration for rule encrypted-volumes exists

TODOs

Read the Gruntwork contribution guidelines.

• Update the docs.
• Run the relevant tests successfully, including pre-commit checks.
• Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
• Include release notes. If this PR is backward incompatible, include a migration guide.
• Attention Grunts - if this PR adds support for a new resource, ensure the nuke_sandbox and nuke_phxdevops jobs in .circleci/config.yml have been updated with appropriate exclusions (either directly in the job or via the .circleci/nuke_config.yml file) to prevent nuking IAM roles, groups, resources, etc that are important for the test accounts.

Release Notes (draft)

Added / Removed / Updated [X].

Migration Guide